Transaction sensitive access network discovery and selection

ABSTRACT

Transaction sensitive access network discovery and selection function (TSANDSF) features are disclosed. TSANDSF features can include access network resource (ANR) selection based on vendor ANR information and UE information. TSANDSF features can further include facilitating access, via a UE, to vendor value added products or service, vendor selected information, or vendor advertisements as a result of establishing a communication link with a vendor ANR. In contrast to conventional ANDSF, TSANDSF can facilitate improved ANR ranking and selection based on rules that correlate UE information with determined vendor ANR features.

TECHNICAL FIELD

The disclosed subject matter relates to access network discovery andselection, including transaction sensitive access network discovery andselection.

BACKGROUND

By way of brief background, access network discovery and selectionfunction (ANDSF) techniques aid user equipment (UE) to discovernon-cellular access networks. These access networks can include Wi-Fi,WiMax, etc. Conventional ANDSF technology can provide network selectionrules and a list of access networks to a UE. This information cantypically be provided by either a push or pull method, e.g., theinformation can be pushed to UEs without a request for the information,or can be pulled to the UE in response to a request by the UE. Numerousimplementations of ANDSF functionality have been implemented. Typically,these implementations employ servers located in the core network of acellular service provider, e.g., ANDSF functionality can be included ina home location register (HLR), etc.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of a system that facilitates determiningtransaction sensitive ANDSF information in accordance with aspects ofthe subject disclosure.

FIG. 2 is a depiction of a system that facilitates determiningtransaction sensitive ANDSF information based on information receivedvia a vendor access network resource component in accordance withaspects of the subject disclosure.

FIG. 3 illustrates a system that facilitates determining transactionsensitive ANDSF information based on information received via a vendoraccess network resource component and facilitating updating of acustomer profile in accordance with aspects of the subject disclosure.

FIG. 4 illustrates an example system that facilitates transactionsensitive ANDSF functionality via a transaction sensitive ANDSFcomponent located at a device located in a network provider-sidecomponent in accordance with aspects of the subject disclosure.

FIG. 5 illustrates a method that facilitates access to access networkresource selection information based on determining transactionsensitive ANDSF information in accordance with aspects of the subjectdisclosure.

FIG. 6 illustrates a method that facilitates determining transactionsensitive ANDSF information based on device parameter information,device software environment information, vendor value added information,and vendor access network resource information in accordance withaspects of the subject disclosure.

FIG. 7 depicts a method facilitating determining transaction sensitiveANDSF information based on user profile information, from a UE, receivedvia a customer profile information component of a vendor access networkresource component in accordance with aspects of the subject disclosure.

FIG. 8 illustrates a method facilitating updating user profileinformation at a UE, via a vendor access network resource component, inresponse to receiving an access network resource rank by the vendoraccess network resource component in accordance with aspects of thesubject disclosure.

FIG. 9 depicts a schematic block diagram of a computing environment withwhich the disclosed subject matter can interact.

FIG. 10 illustrates a block diagram of a computing system operable toexecute the disclosed systems and methods in accordance with anembodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

An access network discovery and selection function (ANDSF) can aid userequipment (UE) to discover non-cellular access networks. These accessnetworks can include Wi-Fi, WiMax, etc. Conventional ANDSF technologycan push or pull network selection rules and a list of access networksto a UE. Typically, ANDSF implementations employ servers located in acore network of a cellular service provider, such as at an HLR, etc.Conventional ANDSF functionality can be ignorant of value added benefitsassociated with selection of an access network resource (ANR) associatedwith a particular vendor. As a non-limiting example, a coffee vendor canprovide access to a higher speed Wi-Fi access point based on a customerloyalty account. Conventional ANDSF technology can be ignorant of ANRsassociated with the example coffee vendor and can also be unable toselect the example higher speed Wi-Fi access point based on determiningthe customer's UE is associated with the customer loyalty account. Incontrast, the presently disclosed subject matter can receive mobiledevice information that can aid in identifying participation in theexample customer loyalty program, identifying the presence of the coffeevendor ANRs, including the example higher speed Wi-Fi access point, andcan aid in selection of the higher speed Wi-Fi access point based, forexample, on a determination that this ANR satisfies a rule related toranked ANRs proximate to the UE.

Transaction sensitive ANDSF technology, as disclosed, can be animprovement to conventional ANDSF technology by providing for improvedANR detection, for example, by receiving updated ANR information fromvendor-side components. Transaction sensitive ANDSF technology can alsobe an improvement to conventional ANDSF technology by providing forimproved ANR selection, for example, by determining selection based onvalue added features, user preferences related to vendor ANRs, fitnessof a vendor ANR to the state of a UE, and other aspects not consideredin conventional ANDSF technologies. Moreover, determination of ANRselection information can be performed more quickly because selectioncriteria related to vendors, and transaction therewith, can result inreduced set sizes employed in the determination of the ANR selectioninformation. As an example, where a UE is executing an electronicbanking function, a subset of ANRs can be employed in determining ANRselection information, wherein the subset comprises a Wi-Fi access pointvia a national banking chain location having a high level of dataencryption as a value added feature. In this example, the value addedfeature can facilitate an ANR sort to exclude many other ANRs that donot offer the high level of data encryption value added feature,resulting in a smaller subset of ANRs for ranking. This can improveprocessing times for ranking and returning a list of ranked ANRs to theUE as part of ANR selection information. In contrast, conventional ANDSFsystems may not facilitate sorting ANRs in view of vendor ANRinformation to determine a subset and, as such, can result in longerprocesses to determine selection information to return to the UE.

Certain embodiments of the present disclosure provide for transactionsensitive ANDSF technology employing current UE device states indetermining ANR selection information. Current UE device states caninclude information about the hardware and software environments of theUE. This current information can reflect a resource need or resourcepreference that can be provided by an ANR, and selection of anappropriate ANR can be facilitated by analyzing resources associatedwith equipment of different vendors. As an example, where a UE isassociated with a user currently searching restaurant reviews, foodvendor ANRs can have increased ranks. An increased rank in the examplefood vendor ANRs can be associated with discounts on purchases with thevendor for UEs that link with the vendor's ANR, targeted advertisingbeing included via UEs that link with the vendor's ANR, access to vendorinformation, such as, menus, reviews, etc., via a UE that links with thevendor's ANR, etc.

In some embodiments of the present disclosure, transaction sensitiveANDSF technology, can employ historical UE device states in determiningANR selection information. Historical UE device states can includeinformation about the historical hardware and historical softwareenvironments of the UE. This historical information can reflect aresource need or resource preference that can be sourced by an ANR, andselection of an appropriate ANR can be facilitated by analyzingresources associated with devices of different vendors. As an example,where a UE is associated with a historical frequent use of low latencyANRs, vendor ANRs can have an increased rank where they are associatedwith low latency. An increase in the example vendor ANR rank can beassociated with historical information related to low latency levels onthat vendor's ANR. As an example, an ANR associated with a branded cableinternet backbone can indicate low latency levels in comparison to anANR associated with a gas station that doesn't indicate any informationabout latency levels. This can steer the UE towards establishing a linkto the branded cable internet backbone ANR. Moreover, where the UE linkswith said ANR, customer interaction can be provided via the UE from thevendor to a user of the UE, such as, advertising, discounts, datacollection, surveys, loyalty programs, news, weather information,traffic information, etc.

Some embodiments of the present disclosure provide transaction sensitiveANDSF technology that can employ predicted UE device states, e.g.,inferences on likely future UE states, in determining ANR selectioninformation. Predicted UE device states can include information aboutlikely future hardware and likely future software environments of theUE. This inference information can reflect a resource need or resourcepreference that can be satisfied by an ANR, and selection of anappropriate ANR can be facilitated by analyzing resources associatedwith ANR devices of different vendors. As an example, where a UE isassociated with an inference of a depleted battery, vendor ANRs can havean increased rank where they are associated with an available powersource. An increase in the example vendor ANR rank can be associatedwith predictive information related to a way to recharge a battery basedon the inference that the battery will be discharged below a determinedlevel. As an example, an ANR associated with a charging station in anairport can be higher ranked than an ANR not associated with a chargingstation in the same airport. The inference of depleted batteryconditions for the UE can be employed to suggest that the UE establish alink to the charging station ANR. Moreover, where the UE links with saidcharging station ANR, the vendor can provide notice via the UE thatpower is available for recharging. In contrast, where an example UE isassociated with a future state having a nearly full battery, the ANRselection information can steer then to the example ANR not associatedwith a charging station and hence, information about available power maynot be provided via the UE. This can result in selectively providingcharging station information to UEs that are more likely to needrecharging and can result in fewer UEs that are not in need of chargingoccupying charging stations, which can be particularly beneficial tousers in areas where charging stations can be a sparse resource.

Certain embodiments of the present disclosure provide transactionsensitive ANDSF technology that can employ event information, e.g.,sporting event information, sale even information, traffic eventinformation, weather event information, etc., in determining ANRselection information. UE device information or vendor information caninclude event information. This event information can reflect a resourceneed or resource preference that can be satisfied by an ANR, andselection of an appropriate ANR can be facilitated by analyzingresources associated with ANR devices of different vendors. As anexample, where event information comprises traffic accident information,vendor ANRs can have an increased rank where they provide added valuethat can mitigate the effects of the traffic accident. An increase inthe example vendor ANR rank can be associated with providing an addedvalue, such as a meal discount, being located closer to a trafficincident, etc., when the traffic accident information satisfies a rule.As an example, an ANR associated with a roadside restaurant near theaccident can be higher ranked than an ANR associated with a restaurantlocated farther from the accident. The event information can be employedto suggest that the UE establish a link to an ANR to capture the addedvalue. Where the user of the UE may prefer to sit in a restaurant towait out a traffic jam caused by the example traffic accident, linkingto the ANR of the example restaurant can allow the vendor to notify theuser, vie the UE, of the example discount associated with the trafficaccident event information. As another example, ANRs associated with ahotel chain can be higher ranked as a result of a severe weather event,a tavern ANR can be higher ranked as a result of a sporting event, ANRsassociated with a government agency can be ranked higher as a result ofa natural disaster event such as flooding, fire, earthquake, etc.,allowing these vendors to interact with UEs that select thecorresponding ANR. This can allow for dissemination of advertising,news, emergency information, amber alerts, etc.

Transaction sensitive ANDSF components can comprise a ranking componentor sorting component that can operate on a set of ANRs. Sorting orranking of ANRs can be beneficial to a network provider by placing anANR in a position that satisfies the needs of a UE with less waste. Asan example, where three ANRs, having a 128 kbs, a 512 kbs, and a 5 mbpschannel correspondingly available to a UE that is streaming music at 256kbs, the ANRs can be ranked 512 kbps, 5 mbps, 128 kbps. This canindicate that use of the 512 kbps is preferable so as not to occupy the5 mbps channel in an underutilized manner, and to try to avoid the 128kbps channel which could cause the UE to change streaming rates tocontinue to stream music over the lower rate channel. In an aspect, thesorting or ranking can also employ mobile device information or vendoraccess network resource information. As an example, device informationcan comprise a user preference for channels with rates of 256 kbps orlower for music streaming processes, which information can be employedin ranking the three ANRs of the prior example as 128 kbps, 512 kbps, 5mbps, to conform with the example user preference and example carrierefficiency goals. As another example, vendor access network resourceinformation can comprise value added content for channels with rates of256 kbps or lower, which information can be employed in ranking thethree ANRs of the prior example as 128 kbps, 512 kbps, 5 mbps, toconform with the example mobile device information and example vendoraccess network resource information.

To the accomplishment of the foregoing and related ends, the disclosedsubject matter, then, comprises one or more of the features hereinaftermore fully described. The following description and the annexed drawingsset forth in detail certain illustrative aspects of the subject matter.However, these aspects are indicative of but a few of the various waysin which the principles of the subject matter can be employed. Otheraspects, advantages and novel features of the disclosed subject matterwill become apparent from the following detailed description whenconsidered in conjunction with the provided drawings.

FIG. 1 is an illustration of a system 100, which facilitates determiningtransaction sensitive ANDSF information in accordance with aspects ofthe subject disclosure. System 100 can include transaction sensitiveANDSF (TSANDSF) component 110. TSANDSF component 110 can receive devicemobile information 122. Mobile device information 122 can comprisedevice hardware environment information or device software environmentinformation related to a UE, a user or user profile associated with theUE, information about processes of the UE, or other information relatedto the UE or user. TSANDSF component 110 can receive vendor accessnetwork resource (VANR) information 132. VANR information 132 cancomprise vendor value added information or vendor access networkresource (ANR) parameter information related to an access networkresource, related to a vendor service or product related thereto,account information related to an a UE or user profile, etc. Someembodiments can also receive ANDSF information from core networkcomponents, etc., not illustrated, see FIG. 2, FIG. 3, etc.

TSANDSF component 110 can facilitate determining ANR selectioninformation 140. ANR selection information 140 can comprise informationrelated to an ANR or a set of ANRs. The information can relate toordered, filtered, or sorted ANRs, and reflect a suggested orprioritized ANR in accord with TSANDSF functionality. ANR selectioninformation 140 can be based on VANR information 132, which can comprisecurrent or historical vendor ANR information, such as, ANR networkcongestion, available ANRs, billing agreements for ANRs with a networkprovider, vendor-centric selection rules, etc. ANR selection information140 can also be based on mobile device information 122, which cancomprise an identifier, location information, motion information, timeinformation, predicted location information, schedule information, anencryption key, financial information, billing information, informationrelated to a process in execution on the UE, QoE or QoS information,service tier information, user preferences, security information,privacy information, device hardware information, device softwareinformation, a behavior model, access network resource information, etc.As an example, ANR selection information 140 can identify a localfemtocell based on VANR information 132 comprising informationindicating low vendor network congestion, availability of the femtocellat the device location, available femtocell resources, and a serviceassociated with the femtocell, and mobile device information 122comprising information indicating that a mobile device has a keyallowing access to the femtocell, the level of service of the mobiledevice is acceptable in view of the available femtocell resources, andmotion data for the UE indicating a low likelihood of moving out ofrange of the femtocell. The example femtocell can be associated with aranking or ordering that can relate to a selection order of the ANR,e.g., example femtocell. Example ANR selection information 140 canfurther comprise ANR information for other ANRs. These can also beranked or sorted to reflect a preferred selection order relative to theranked or ordered example femtocell in view of the mobile deviceinformation, e.g., mobile device information 122, and the VANRinformation, e.g., VANR information 132.

TSANDSF component 110 can further rank or order vendor ANRs againstANDSF information, such as ANDSF information received from a corenetwork component associated with a cellular service provider corenetwork. As such, TSANDSF component 110 can extend functionalityassociated with conventional ANDSF technology. In an embodiment, TSANDSFcomponent can function in parallel with conventional ANDSF components toprovide increased functionality for a UE proximate to an ANR associatedwith VANR information. As such, in some embodiments, a conventionalANDSF component can provide selection information that is ignorant ofVANR information 132 to some UEs and TSANDSF component 110 cancontemporaneously provide ANR selection information 140 to a UE that canbe based on VANR information 132 and further based on conventional ANDSFinformation. As an example, a first UE can receive ANR selectioninformation 140 via TSANDSF component 110 that considers conventionalANDSF information and VANR information 132 while a second UE can receiveconventional ANDSF information from a conventional ANDSF componentwithout the benefit of analyzing VANR information 132 via TSANDSFcomponent 110.

Mobile device information 132 can comprise, in certain embodiments,current UE device states to enable determining ANR selection information140. Current UE device states can include information about the currenthardware and current software environments of the UE. This currentinformation can reflect a resource need or resource preference soughtfrom an prospective ANR, and selection of an appropriate ANR can befacilitated by analyzing resources associated with equipment ofdifferent vendors. As an example, where a UE is associated with a usercurrently streaming high definition video content, high bandwidth vendorANRs can have increased rankings. An increased rank in the examplevendor ANRs can be associated with providing priority access to the highbandwidth ANR based on an identifier related to a need for a highbandwidth connection from a UE. Where a link with a high bandwidthrequesting UE is made to the vendor ANR, the vendor can additionallysource information to a user via the UE, such as, discounts on purchaseswith the vendor, advertising, access to vendor information, etc.

In some embodiments, transaction sensitive ANDSF technology, can employhistorical UE device states, e.g., as part or mobile device information132, in determining ANR selection information. Historical UE devicestates can include information about the historical hardware andhistorical software environments of the UE. This historical informationcan reflect a resource need or resource preference that can be met by anANR, and selection of an appropriate ANR can be facilitated by analyzingresources associated with ANR devices of different vendors. As anexample, where a UE is associated with a historical frequent use of lowlatency ANRs, vendor ANRs can have an increased rank where they areassociated with low latency. An increase in the example vendor ANR rankcan be associated with historical information related to low latencylevels on that vendor's ANR.

Some embodiments of mobile device information 132 can comprise predictedUE device states, e.g., inferences on likely future UE states, indetermining ANR selection information. Predicted UE device states caninclude information about likely future hardware and likely futuresoftware environment characteristics of a UE. This inference informationcan reflect a resource need or resource preference that can be satisfiedby an ANR, and selection of an appropriate ANR can be facilitated byanalyzing resources associated with ANR devices of different vendors. Asan example, where a UE is associated with an inference of a depletedbattery, vendor ANRs can have an increased rank where they areassociated with an available power source as a value added feature. Anincrease in the example vendor ANR rank can be associated withpredictive information related to a way to recharge a battery based onthe inference that the battery will be depleted at a future time. As anexample, an ANR associated with a charging station in an airport can behigher ranked than an ANR not associated with a charging station in thesame airport. The inference of depleted battery conditions for the UEcan be employed to suggest that the UE establish a link to the chargingstation ANR. Moreover, where the UE links with said charging stationANR, the vendor can provide notice via the UE that power is availablefor recharging. In contrast, where an example UE is associated with afuture state having a nearly full battery, the ANR selection informationcan steer then to the example ANR not associated with a charging stationand hence, information about available power may not be provided via theUE. This can result in selectively providing charging stationinformation to UEs that are more likely to need recharging and canresult in fewer UEs that are not in need of charging occupying chargingstations, which can be particularly beneficial to users in areas wherecharging stations can be a sparse resource.

Certain embodiments of the present disclosure provide transactionsensitive ANDSF technology that can employ event information, e.g.,sporting event information, sale even information, traffic eventinformation, weather event information, etc., in determining ANRselection information. UE device information or vendor information caninclude event information. This event information can reflect a resourceneed or resource preference that can be satisfied by an ANR, andselection of an appropriate ANR can be facilitated by analyzingresources associated with ANR devices of different vendors. As anexample, where event information comprises traffic accident information,vendor ANRs can have an increased rank where they provide added valuethat can mitigate the effects of the traffic accident. An increase inthe example vendor ANR rank can be associated with providing an addedvalue, such as a meal discount, being located closer to a trafficincident, etc., when the traffic accident information satisfies a rule.As an example, an ANR associated with a roadside restaurant near theaccident can be higher ranked than an ANR associated with a restaurantlocated farther from the accident. The event information can be employedto suggest that the UE establish a link to an ANR to capture the addedvalue. Where the user of the UE may prefer to sit in a restaurant towait out a traffic jam caused by the example traffic accident, linkingto the ANR of the example restaurant can allow the vendor to notify theuser, vie the UE, of the example discount associated with the trafficaccident event information. As another example, ANRs associated with ahotel chain can be higher ranked as a result of a severe weather event,a tavern ANR can be higher ranked as a result of a sporting event, ANRsassociated with a government agency can be ranked higher as a result ofa natural disaster event such as flooding, fire, earthquake, etc.,allowing these vendors to interact with UEs that select thecorresponding ANR. This can allow for dissemination of advertising,news, emergency information, amber alerts, etc.

FIG. 2 is a depiction of a system 200 that can facilitate determiningtransaction sensitive ANDSF information based on information receivedvia a vendor access network resource component in accordance withaspects of the subject disclosure. System 200 can include transactionsensitive ANDSF (TSANDSF) component 210. TSANDSF component 210 can becoupled to mobile device 220. Mobile device 220 can be a user equipment,such as, a smartphone, a cellphone, a tablet computer, a wearabledevice, a laptop computer, etc. Mobile device can receive ANR selectioninformation 240 to enable selection of an ANR based on TSANDSF analysis.Information related to the mobile device 220 can comprise devicehardware environment information or device software environmentinformation related to a UE, a user or user profile associated with aUE, information about processes of a UE, or other information related toa UE or user.

Mobile device 220 can comprise device parameter information component(DPIC) 224. DPIC 224 can facilitate access to device parameterinformation. Device parameter information can comprise device hardwareenvironment information. As such, device parameter information cancomprise information related to processor speeds, memorycharacteristics, display parameters, accelerometer measurements,barometric measurements, temperature measurements, location, motion,user interface features, radio technologies of the device, batterylevels and health, etc. In an aspect, DPIC 224 can facilitate access tonearly any information related to the physical state, environment, orfeature of a UE to facilitate TSANDSF functionality in determining ANRselection information 240. As an example, DPIC 224 can facilitate accessto temperature/weather information that can indicate cold windy weatherbased on UE sensor data. This example information can be employed byTSANDSF component 210 in conjunction with information from VANRcomponent 230 to increase the rank of a vendor ANR associated with awarm room, hot drinks or food, warm clothing, etc. In contrast to aconventional ANDSF system that might merely suggest a nearby ANR withoutany consideration to value added vendor features, the exampleinformation can be leverage in by TSANDSF 210 to increase the ranks ofvendor ANRs that also proved added value when selected.

In some embodiments, mobile device 220 can comprise device softwareenvironment information component (DSEIC) 226. DSEIC 226 can facilitateaccess to device software environment information. As such, DSEIC 226can facilitate access to information that can comprise informationrelated to processes in execution, active processes, inactive processes,stalled processes, connectivity requirements or preferences, memoryaccess characteristics, user interface parameters, software versions,update status, etc. In an aspect, DSEIC 226 can facilitate access tonearly any information related to the software state, softwareenvironment, or software features of a UE to facilitate TSANDSFfunctionality in determining ANR selection information 240. As anexample, DSEIC 226 can facilitate access to information indicating thata UE is running a beta-test version of an operating system having highburst transmission characteristics. This example information can beemployed by TSANDSF component 210 in conjunction with information fromVANR component 230 to increase the rank of a vendor ANR associated withan ANR optimized for the beta-test version of the OS adapted to acceptthe high burst data transmissions, etc. In contrast to a conventionalANDSF system that might merely suggest a nearby ANR without anyconsideration to value added vendor features, the example informationcan be leveraged by TSANDSF 210 to increase the rank of a vendor ANRthat also provides added value when selected. In this example, selectingthe designated ANR can allow the UE to operate more efficiently byenabling the high burst data transmission of the beta-test OS via theexample vendor ANR.

TSANDSF component 210 can be coupled to vendor access network resource(VANR) component 230. VANR component 230 can facilitate access to vendorvalue added information via vendor value added information component(VVAIC) 234 or vendor ANR parameter information, via vendor ANRparameter information component (VANRPIC) 236. VANRPIC 236 canfacilitate access to ANR parameter information, such as, radiotechnology information, ANR software characteristics or parameters, ANRutilization information, ANR connectivity information, etc. VANRPIC 236can, in an aspect, enable access to information related to theenvironment of, operation of, or features of the vendor ANR.

VVAIC 234 can facilitate access to vendor value added informationrelated to a vendor access network resource, a vendor service or productrelated thereto, account information related to an a UE or user profile,etc. VVAIC 234 can enable access to information relating to additionalbenefits associated with selecting a vendor ANR. As such, VVAIC 234 canprovide for access to information that, for example, a vendor ANRemploys strong encryption, a vendor complies with high levels ofprivacy, a vendor offers free or discounted products to users of thevendor's ANR, that a vendor ANR guarantees a level oflatency/bandwidth/jitter/etc., that a vendor ANR employs a designatedcommunications standard, that a vendor location associated with thevendor's ANR has services or products available, etc. As a non-limitingexample, VVAIC 234 can allow access to information indicating that aninternet café employs anonymous routing technology as a value addedfeature to provide anonymity to users who link their UEs to the internetcafé's ANR, which can distinguish the internet café from other vendorsthat may not provide anonymity via their ANRs.

TSANDSF component 210 can facilitate determining ANR selectioninformation 240. ANR selection information 240 can comprise informationrelated to an ANR or a set of ANRs. The information can relate toordered, filtered, or sorted ANRs, and reflect a suggested orprioritized ANR in accord with TSANDSF functionality. ANR selectioninformation 240 can be based on information received via VANR component230, which can comprise current or historical information from VVAIC 234or VANRPIC 236. ANR selection information 240 can also be based oncurrent or historical information related to mobile device 220, e.g.,access via DPIC 224 or DSEIC 226.

DPIC 224 or DSEIC 226 can enable access to mobile device informationthat can comprise, in certain embodiments, current UE device states toenable determining ANR selection information 240. Current UE devicestates can include information about the current hardware and currentsoftware environments of the UE. This current information can reflect aresource need or resource preference sought from a prospective ANR, andselection of an appropriate ANR can be facilitated by analyzingresources associated with equipment of different vendors.

In some embodiments, DPIC 224 or DSEIC 226 can enable access tohistorical UE device states as part of determining ANR selectioninformation. Historical UE device states can include information aboutthe historical hardware and historical software environments of the UE.This historical information can reflect a resource need or resourcepreference that can be met by an ANR, and selection of an appropriateANR can be facilitated by analyzing resources associated with ANRdevices of different vendors.

Some embodiments of DPIC 224 or DSEIC 226 can facilitate access topredicted UE device states, such as, inferences relating to likelyfuture UE states, in conjunction with determining ANR selectioninformation. Predicted UE device states can include information aboutlikely future hardware and likely future software environmentcharacteristics of a UE. This inference information can reflect apredicted resource need or resource preference that can be satisfied byan ANR, and selection of an appropriate ANR can be facilitated byanalyzing resources associated with ANR devices of different vendors.

Certain embodiments of the present disclosure provide for DPIC 224,DSEIC 226, or VVAIC 234, that can enable access to event information tofacilitate determining ANR selection information. As such, UE deviceinformation or vendor information can comprise event information. Thisevent information can reflect a resource need or resource preferencethat can be satisfied by an ANR, and selection of an appropriate ANR canbe facilitated by analyzing resources associated with ANR devices ofdifferent vendors. Event information can be employed to suggest that theUE establish a link to an ANR to capture added value corresponding to anevent via a vendor or vendor ANR.

TSANDSF component 210 can further rank or order vendor ANRs,conventional ANDSF information, or a combination thereof. As such,TSANDSF component 210 can comprise ANR ranking component (ARC) 250. ARC250 can analyze information received from mobile device 220 or VANRcomponent 230 to rank a vendor ANR. Moreover, in some embodiments, ANDSFinformation access component 260 can enable access to conventional ANDSFinformation, e.g., from a conventional ANDSF component locatedelsewhere. Where conventional ANDSF information is received, ARCcomponent 250 can also facilitate ranking this information. As satedherein, ranking ANRs associated with conventional ANDSF information canbe separate from, in parallel with, or in conjunction with ranking of avendor ANR.

FIG. 3 illustrates a system 300 that facilitates determining transactionsensitive ANDSF information based on information received via a vendoraccess network resource component and facilitating updating of acustomer profile in accordance with aspects of the subject disclosure.System 300 can include transaction sensitive ANDSF (TSANDSF) component310. TSANDSF component 310 can be coupled to mobile device 320. Mobiledevice 320 can be a user equipment, such as, a smartphone, a cellphone,a tablet computer, a wearable device, a laptop computer, etc. Mobiledevice 320 can receive ANR selection information 340 to enable selectionof an ANR based on TSANDSF analysis. Information related to mobiledevice 320 can comprise device hardware environment information ordevice software environment information related to a UE, a user or userprofile associated with a UE, information about processes of a UE, orother information related to a UE or user.

Mobile device 320 can comprise device parameter information component(DPIC) 324. DPIC 324 can facilitate access to device parameterinformation. Device parameter information can comprise device hardwareenvironment information. As such, device parameter information cancomprise information related to processor speeds, memorycharacteristics, display parameters, accelerometer measurements,barometric measurements, temperature measurements, location, motion,user interface features, radio technologies of the device, batterylevels and health, etc. In an aspect, DPIC 324 can facilitate access tonearly any information related to the physical state, environment, orfeature of a UE to facilitate TSANDSF functionality in determining ANRselection information 340.

In some embodiments of system 300, mobile device 320 can comprise userprofile information component 328. User profile information component328 can facilitate access to information associated with a user profile.In some instances, user profile information component 328 can comprise amemory for storing a user profile. In some embodiments, user profileinformation component 328 can receive information from a user profilestored on another component. User profile information can compriseinformation related to user related preferences, user related facts, anduse and user related opinions. User profile information can beconsidered in a TSANDSF analysis relating to selection of an ANR. As anexample, user profile information component 328 can facilitate receivinginformation indicating that a user has a preference for a brand ofclothing. This clothing brand preference can be shared with TSANDSFcomponent 310 and considered in ANR ranking via ARC 350 in view of VVAIC334 related information. Where VVAIC 334 related information indicatesthat the preferred clothing brand is associated with an ANR, this canincrease the ranking of said ANR. As such, where the UE is establishes alink with said ANR, information, advertisements, discounts, etc., forexample, those related to the brand of clothing, those related tocomplimentary products, services, and experiences, etc., can be relayedby the vendor to the user via the UE.

TSANDSF component 310 can be coupled to vendor access network resource(VANR) component 330. VANR component 330 can facilitate access to vendorvalue added information via vendor value added information component(VVAIC) 334 or vendor ANR parameter information, via vendor ANRparameter information component (VANRPIC) 336. VANRPIC 336 canfacilitate access to ANR parameter information, such as, radiotechnology information, ANR software characteristics or parameters, ANRutilization information, ANR connectivity information, etc. VANRPIC 336,in an aspect, can enable access to information related to theenvironment of, operation of, or features of the vendor ANR.

VVAIC 334 can facilitate access to vendor value added informationrelated to a vendor access network resource, a vendor service or productrelated thereto, account information related to an a UE or user profile,etc. VVAIC 334 can enable access to information relating to additionalbenefits associated with selecting a vendor ANR. As such, VVAIC 334 canprovide for access to information that, for example, a vendor ANRemploys strong encryption, a vendor complies with high levels ofprivacy, a vendor offers free or discounted products to users of thevendor's ANR, that a vendor ANR guarantees a level oflatency/bandwidth/jitter/etc., that a vendor ANR employs a designatedcommunications standard, that a vendor location associated with thevendor's ANR has services or products available, etc.

VANR component 330 can also comprise customer profile informationcomponent 338. Customer profile information component 338 can facilitateaccess to information associated with a customer profile. In someinstances, customer profile information component 338 can comprise amemory for storing a customer profile. In some embodiments, customerprofile information component 338 can receive information from acustomer profile stored on another component. Customer profileinformation can comprise information related to customer relatedpreferences, customer related facts, and use and customer relatedopinions. Customer profile information can be considered in a TSANDSFanalysis relating to selection of an ANR. As an example, customerprofile information component 338 can facilitate receiving informationindicating that a customer has a preference for a style of music. Thismusic preference can be shared with TSANDSF component 310 and consideredin ANR ranking via ARC 350 in view of related information received frommobile device 320, e.g., via user profile information component 328.Where information related to mobile device 320 indicates that thepreferred music style is associated with an ANR, this can increase theranking of said ANR. As such, where a UE is establishes a link with saidANR, information, advertisements, discounts, etc., for example, thoserelated to the style of music, those related to complimentary products,services, and experiences, etc., can be relayed by the vendor to theuser via the UE.

In some embodiments, user profile information component 328 and customerprofile information component 328 can share information, eitherdirectly, via TSANDSF component 310, or via another pathway. In certainembodiments, user profile information component 328 and customer profileinformation component 328 can access information from the same datastore. In other embodiments, user profile information component 328 canupdate information associated with customer profile informationcomponent 328. In some embodiments, customer profile informationcomponent 328 can update information associated with user profileinformation component 328. As such, user profile information component328 and customer profile information component 328 can be updated toreflect information related to user preferences and customerpreferences. As an example, a user can indicate a preference for a brandof coffee, which information can be populated into a customer profilefor vendors of the same brand of coffee, other brands of coffee, ofcomplimentary products, etc. As another example, a customer profile canreflect buying trends for customers, which information can be populatedinto a user profile even where the user isn't capable of determining thebuying trends themselves. This trend information can then be shared withother vendor customer profile information components 338 to propagateinformation that can be effective in helping increase the rank ofaffiliated ANRs. As an example, where the user usually buys organic milkwith non-organic eggs, this information can be determined by customerprofile component 338 and shared with user profile information component328. Further, the example information can then be shared with othercustomer profile information components to aid in determining a heistranked ANR as relates to eggs and milk, such as offering a vendordiscount on organic eggs when the UE links to a grocers ANR and scans ina bar code from an organic milk container, in an attempt to have thecustomer/user try organic eggs rather than regular eggs.

TSANDSF component 310 can facilitate determining ANR selectioninformation 340. ANR selection information 340 can comprise informationrelated to an ANR or a set of ANRs. The information can relate toordered, filtered, or sorted ANRs, and reflect a suggested orprioritized ANR in accord with TSANDSF functionality. ANR selectioninformation 340 can be based on information received via VANR component330, which can comprise current or historical information from VVAIC334, VANRPIC 336, or customer profile information component 338. ANRselection information 340 can also be based on current or historicalinformation related to mobile device 320, e.g., received via DPIC 324,DSEIC 326, or user profile information component 328.

DPIC 324, DSEIC 326, or user profile information component 328 canenable access to mobile device information that can comprise, in certainembodiments, current UE device states to enable determining ANRselection information 340. Current UE device states can includeinformation about the current hardware and current software environmentsof the UE. This current information can reflect a resource need orresource preference sought from an prospective ANR, and selection of anappropriate ANR can be facilitated by analyzing resources associatedwith equipment of different vendors.

In some embodiments, DPIC 324, DSEIC 326, or user profile informationcomponent 328 can enable access to historical UE device states as partof determining ANR selection information. Historical UE device statescan include information about the historical hardware and historicalsoftware environments of the UE. This historical information can reflecta resource need or resource preference that can be met by an ANR, andselection of an appropriate ANR can be facilitated by analyzingresources associated with ANR devices of different vendors.

Some embodiments of DPIC 324, DSEIC 326, or user profile informationcomponent 328 can facilitate access to predicted UE device states, suchas, inferences relating to likely future UE states, in conjunction withdetermining ANR selection information. Predicted UE device states caninclude information about likely future hardware and likely futuresoftware environment characteristics of a UE. This inference informationcan reflect a predicted resource need or resource preference that can besatisfied by an ANR, and selection of an appropriate ANR can befacilitated by analyzing resources associated with ANR devices ofdifferent vendors.

Certain embodiments of the present disclosure provide for DPIC 324,DSEIC 326, user profile information component 328, VVAIC 334, orcustomer profile information component 338, to enable access to eventinformation to facilitate determining ANR selection information. Assuch, UE device information or vendor information can comprise eventinformation. This event information can reflect a resource need orresource preference that can be satisfied by an ANR, and selection of anappropriate ANR can be facilitated by analyzing resources associatedwith ANR devices of different vendors. Event information can be employedto suggest that the UE establish a link to an ANR to capture added valuecorresponding to an event via a vendor or vendor ANR.

TSANDSF component 310 can further rank or order vendor ANRs,conventional ANDSF information, or a combination thereof. As such,TSANDSF component 310 can comprise ANR ranking component (ARC) 350. ARC350 can analyze information received from mobile device 320 or VANRcomponent 330 to rank a vendor ANR. Moreover, in some embodiments, ANDSFcomponent 360 can enable access to conventional ANDSF information. Whereconventional ANDSF information is received, ARC component 350 can alsofacilitate ranking this information. As sated herein, ranking ANRsassociated with conventional ANDSF information can be separate from, inparallel with, or in conjunction with ranking of a vendor ANR.

FIG. 4 illustrates example system 400 that facilitates transactionsensitive ANDSF functionality via a transaction sensitive ANDSFcomponent located at a device located in a network provider-sidecomponent in accordance with aspects of the subject disclosure. System400 can include transaction sensitive ANDSF component 410 located at anetwork provider-side component 412 which can be linked to UE 420 via acommunication framework and radio device 440. UE 420 can be linked toradio device 440 wirelessly, e.g., by a cellular connection, etc. UE 420can receive ANR selection information ranking ANR 450, 452, 454, etc.,to enable UE 420 in selecting and establishing a link with said ANRswhere determined to be appropriate. Moreover, system 400 can illustrateseveral configurations implementing VANR components, e.g., VANRcomponent 430, 432, and 434. VANR components 430, 432, and 434, canfacilitate TSANDSF analysis of ANRs 450, 452, 454, etc., as part ofdetermining ANR selection information.

ANR 450 can be associated with vendor-side component 490, such as avendor router, vendor server, etc. ANR 450 can be coupled to VANRcomponent 430 via vendor-side component 490. VANR component 430 cansource information to TSANDSF component 410 via wireless link to UE 420.UE 420 can source information to TSANDSF component 410, comprisingdevice information and VANR information, via radio device 440 and thecommunication framework. This information can be employed in determiningANR selection information.

ANR 452 can be associated with vendor-side component 492. ANR 452 can becoupled to VANR component 432 via vendor-side component 492. In someembodiments, VANR component 432 can be located on the vendor side of thecommunications framework. In certain embodiments, VANR component 432 canbe located remote from vendor-side component 492 and remote from networkprovider-side component 412. In other embodiments, VANR component 432can be located on the network provider-side of the communicationsframework (not illustrated). VANR component 432 can source informationto TSANDSF component 410 via a link to network provider-side component412 via the communications framework. UE 420 can source information toTSANDSF component 410 via radio device 440 and the communicationframework. This information can be employed in determining ANR selectioninformation.

ANR 454 can be associated with vendor-side component 494. ANR 454 can becoupled to vendor-side component 494, which can comprise VANR component434. In some embodiments, vendor-side component 494 can be located nearANR 454. In certain embodiments, vendor-side component 494 can belocated remotely from ANR 454. VANR component 434 can source informationto TSANDSF component 410 via a link to network provider-side component412 via the communications framework. UE 420 can source information toTSANDSF component 410 via radio device 440 and the communicationframework. This information can be employed in determining ANR selectioninformation.

TSANDSF component 410 can determine ranking information for ANR 450,452, and 454, based on device information from UE 420 and VANRinformation from VANR component 430, 432, and 434. Ranking informationfor ANR 450, 452, and 454, can further be based on conventional ANDSFinformation (not illustrated) received by TSANDSF component 410 asdiscussed herein. The ranking information can be employed in determiningANR selection information that can be received by UE 420. This ANRselection information can enable UE 420 to establish a link with ANR450, 452, or 454 that reflects vendor value added aspects, devicerelated information, and user related information as disclosed herein.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 5-FIG. 8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 5 illustrates a method 500 that facilitates accessing accessnetwork resource selection information based on determining transactionsensitive ANDSF information. At 510, method 500 can include receivingdevice information. Device information can comprise device hardwareenvironment information or device software environment informationrelated to a UE, a user or user profile associated with the UE,information about processes of the UE, or other information related tothe UE or user. In an aspect, device information can comprise anidentifier, location information, motion information, time information,predicted location information, schedule information, an encryption key,financial information, billing information, information related to aprocess in execution on the UE, QoE or QoS information, service tierinformation, user preferences, security information, privacyinformation, device hardware information, device software information, abehavior model, access network resource information, etc. In certainembodiments, device information can comprise current, historical,predictive, or event information as disclosed herein.

At 520, method 500 can comprise receiving vendor access network resource(VANR) information. VANR information can comprise vendor value addedinformation or vendor access network resource (ANR) parameterinformation related to an access network resource, related to a vendorservice or product related thereto, account information related to an aUE or user profile, etc. In some embodiments, VANR information cancomprise event information, as disclosed herein. In certain embodiments,VANR information can comprise current or historical vendor ANRinformation, such as, ANR network congestion, available ANRs, billingagreements for ANRs with a network provider, vendor-centric selectionrules, etc.

At 530, method 500 can comprise determining ANR selection informationbased on the device information and VANR information. Determining ANRselection information can comprise analysis of information related to anANR or a set of ANRs. The information can relate to ordered, filtered,or sorted ANRs, and reflect a suggested or prioritized ANR in accordwith TSANDSF functionality. ANR selection information can be based onVANR information, which can comprise current or historical vendor ANRinformation. ANR selection information can also be based on mobiledevice information. Determining ANR selection information can alsocomprise ranking or ordering an ANR. In some instances, ranking orordering an ANR can comprise ranking or ordering a vendor ANR. Rankingor ordering an ANR can further be based on receiving conventional ANDSFinformation, as disclosed elsewhere herein, such as ANDSF informationreceived from a core network component associated with a cellularservice provider core network. As such, a TSANDSF component can extendfunctionality associated with conventional ANDSF technology. In anembodiment, a TSANDSF component can function in parallel withconventional ANDSF components to provide increased functionality for aUE proximate to an ANR associated with VANR information. As such, insome embodiments, a conventional ANDSF component can provide selectioninformation that is ignorant of VANR information to some UEs and aTSANDSF component can contemporaneously provide ANR selectioninformation to a UE that is based on VANR information and further basedon conventional ANDSF information.

At 540, method 500 can include facilitating access to the ANR selectioninformation. At this point method 500 can end. In some embodiments,access to the ANR selection information can be by a UE, such as thedevice associated with device information from 510.

Device information can comprise, in certain embodiments, current UEdevice states to enable determining ANR selection information. CurrentUE device states can include information about the current hardware andcurrent software environments of the UE. This current information canreflect a resource need or resource preference sought from anprospective ANR, and selection of an appropriate ANR can be facilitatedby analyzing resources associated with equipment of different vendors.

In some embodiments, transaction sensitive ANDSF technology, can employhistorical UE device states, e.g., as part or device information, indetermining ANR selection information. Historical UE device states caninclude information about the historical hardware and historicalsoftware environments of the UE. This historical information can reflecta resource need or resource preference that can be met by an ANR, andselection of an appropriate ANR can be facilitated by analyzingresources associated with ANR devices of different vendors.

Some embodiments of device information can comprise predicted UE devicestates, e.g., inferences on likely future UE states, in determining ANRselection information. Predicted UE device states can includeinformation about likely future hardware and likely future softwareenvironment characteristics of a UE. This inference information canreflect a resource need or resource preference that can be satisfied byan ANR, and selection of an appropriate ANR can be facilitated byanalyzing resources associated with ANR devices of different vendors.

Certain embodiments of the present disclosure provide transactionsensitive ANDSF technology that can employ event information, indetermining ANR selection information. Device information or VANRinformation can include event information. This event information canreflect a resource need or resource preference that can be satisfied byan ANR, and selection of an appropriate ANR can be facilitated byanalyzing resources associated with ANR devices of different vendors.The event information can be employed to suggest that the UE establish alink to an ANR to capture the added value.

FIG. 6 illustrates a method 600 that facilitates determining transactionsensitive ANDSF information based on device parameter information,device software environment information, vendor value added information,and vendor access network resource information. At 610, method 600 caninclude receiving device parameter information. Device parameterinformation can comprise device hardware environment information. Assuch, device parameter information can comprise information related toprocessor speeds, memory characteristics, display parameters,accelerometer measurements, barometric measurements, temperaturemeasurements, location, motion, user interface features, radiotechnologies of the device, battery levels and health, etc. In anaspect, device parameter information can comprise nearly any informationrelated to the physical state, environment, or feature of a UE tofacilitate TSANDSF functionality in determining ANR selectioninformation. In certain embodiments, device parameter information cancomprise current, historical, predictive, or event information asdisclosed herein.

At 620, method 600 can comprise receiving device software environmentinformation. Device software environment information can compriseinformation related to processes in execution, active processes,inactive processes, stalled processes, connectivity requirements orpreferences, memory access characteristics, user interface parameters,software versions, update status, etc. In an aspect, this can facilitateaccess to nearly any information related to the software state, softwareenvironment, or software features of a UE to facilitate TSANDSFfunctionality in determining ANR selection information. In certainembodiments, device parameter information can comprise current,historical, predictive, or event information as disclosed herein.

At 630, method 600 can comprise receiving vendor value addedinformation. This information can be related to a vendor access networkresource, a vendor service or product related thereto, accountinformation related to an a UE or user profile, etc. In someembodiments, vendor value added information can be related to additionalbenefits associated with selecting a vendor ANR. As such, vendor valueadded information can indicate, for example, a vendor ANR employs strongencryption, a vendor complies with high levels of privacy, a vendoroffers free or discounted products to users of the vendor's ANR, that avendor ANR guarantees a level of latency/bandwidth/jitter/etc., that avendor ANR employs a designated communications standard, that a vendorlocation associated with the vendor's ANR has services or productsavailable, etc.

At 640, method 600 can comprise receiving vendor ANR parameterinformation. Vendor ANR parameter information can comprise radiotechnology information, ANR software characteristics or parameters, ANRutilization information, ANR connectivity information, etc. In anaspect, vendor ANR parameter information can be related to theenvironment of, operation of, or features of the vendor ANR.

At 650, method 600 can comprise receiving ANDSF information from anetwork provider component. In some instance, the network providercomponent can be a network provider core component, e.g., can be acomponent located in the core systems associated with the networkprovider. In other instances, the network provider component can be anon-core component, such as, a NodeB, eNodeB, edge server, etc. In someembodiments, ANDSF information from a network provider component can beconventional ANDSF information, which can facilitate ranking ANRsassociated with conventional ANDSF information separate from, inparallel with, or in conjunction with ranking of a vendor ANR, asdisclosed herein.

At 660, method 600 can comprise determining an ANR rank for an ANR basedon ANDSF information, device parameter information, device softwareenvironment information, vendor value added information, and vendor ANRparameter information. Determining rank can further comprise ranking orordering vendor ANRs, ranking or ordering ANRs based on conventionalANDSF information, or a combination thereof. This can comprise ananalysis of information received from a mobile device, e.g., deviceparameter information or device software environment information, orVANR component, e.g., vendor value added information or vendor ANRparameter information, to rank a vendor ANR. Moreover, in someembodiments, access to conventional ANDSF information, e.g., from aconventional ANDSF component located elsewhere can also facilitateranking non-vendor ANRs associated with this conventional information.As sated herein, ranking ANRs associated with conventional ANDSFinformation can be separate from, in parallel with, or in conjunctionwith ranking of a vendor ANR.

At 670, method 600 can comprise determining ANR selection informationbased on the ANR rank information from 660. Determining ANR selectioninformation can comprise analysis of information related to an ANR or aset of ANRs in view of the rank determination for an ANR.

At 680, method 600 can include facilitating access to the ANR selectioninformation. At this point method 600 can end. In some embodiments,access to the ANR selection information can be by a UE, such as thedevice associated with device information from 610.

FIG. 7 illustrates a method 700 that facilitates determining transactionsensitive ANDSF information based on user profile information, from aUE, received via a customer profile information component of a vendoraccess network resource component in accordance with aspects of thesubject disclosure. At 710, method 700 can include receiving deviceparameter information. Device parameter information can comprise devicehardware environment information. As such, device parameter informationcan comprise information related to processor speeds, memorycharacteristics, display parameters, accelerometer measurements,barometric measurements, temperature measurements, location, motion,user interface features, radio technologies of the device, batterylevels and health, etc. In an aspect, device parameter information cancomprise nearly any information related to the physical state,environment, or feature of a UE to facilitate TSANDSF functionality indetermining ANR selection information. In certain embodiments, deviceparameter information can comprise current, historical, predictive, orevent information as disclosed herein.

At 720, method 700 can comprise receiving device software environmentinformation. Device software environment information can compriseinformation related to processes in execution, active processes,inactive processes, stalled processes, connectivity requirements orpreferences, memory access characteristics, user interface parameters,software versions, update status, etc. In an aspect, this can facilitateaccess to nearly any information related to the software state, softwareenvironment, or software features of a UE to facilitate TSANDSFfunctionality in determining ANR selection information. In certainembodiments, device parameter information can comprise current,historical, predictive, or event information as disclosed herein.

At 730, method 700 can comprise receiving user profile information. Userprofile information can, in an embodiment, be received from a userequipment via a customer profile information component. User profileinformation can comprise information related to user relatedpreferences, user related facts, and use and user related opinions. Userprofile information can be considered in a TSANDSF analysis relating toselection of an ANR. A customer profile information component canfacilitate access to information associated with a customer profile.Customer profile information can comprise information related tocustomer related preferences, customer related facts, and use andcustomer related opinions. Customer profile information can beconsidered in a TSANDSF analysis relating to selection of an ANR. Userprofile information and customer profile information can, in someinstances, comprise the same or similar information, for example wherethe information is shared either directly, via a TSANDSF component, orvia another pathway. In certain embodiments, user profile informationand customer profile information can be stored on the same data store orcan be in extracted from the same set of data. In an aspect, a customerprofile information component can facilitate access to user profileinformation.

In some embodiments, user profile information can be used to updatecustomer profile information. In some embodiments, customer profileinformation can be used to update user profile information. As such,user profile information and customer profile information can be updatedto reflect information related to user preferences and customerpreferences.

At 740, method 700 can comprise receiving vendor value addedinformation. This information can be related to a vendor access networkresource, a vendor service or product related thereto, accountinformation related to an a UE or user profile, etc. In someembodiments, vendor value added information can be related to additionalbenefits associated with selecting a vendor ANR. As such, vendor valueadded information can indicate, for example, a vendor ANR employs strongencryption, a vendor complies with high levels of privacy, a vendoroffers free or discounted products to users of the vendor's ANR, that avendor ANR guarantees a level of latency/bandwidth/jitter/etc., that avendor ANR employs a designated communications standard, that a vendorlocation associated with the vendor's ANR has services or productsavailable, etc.

At 750, method 700 can comprise receiving vendor ANR parameterinformation. Vendor ANR parameter information can comprise radiotechnology information, ANR software characteristics or parameters, ANRutilization information, ANR connectivity information, etc. In anaspect, vendor ANR parameter information can be related to theenvironment of, operation of, or features of the vendor ANR.

At 760, method 700 can comprise receiving ANDSF information from anetwork provider component. In some instance, the network providercomponent can be a network provider core component, e.g., can be acomponent located in the core systems associated with the networkprovider. In other instances, the network provider component can be anon-core component, such as, a NodeB, eNodeB, edge server, etc. In someembodiments, ANDSF information from a network provider component can beconventional ANDSF information, which can facilitate ranking ANRsassociated with conventional ANDSF information separate from, inparallel with, or in conjunction with ranking of a vendor ANR, asdisclosed herein.

At 770, method 700 can comprise determining an ANR rank for an ANR basedon ANDSF information, device parameter information, device softwareenvironment information, vendor value added information, vendor ANRparameter information, and user profile information. Determining rankcan further comprise ranking or ordering vendor ANRs, ranking orordering ANRs based on conventional ANDSF information, or a combinationthereof. This can comprise an analysis of information received from amobile device, e.g., device parameter information or device softwareenvironment information, or VANR component, e.g., vendor value addedinformation or vendor ANR parameter information, to rank a vendor ANR.Moreover, in some embodiments, access to conventional ANDSF information,e.g., from a conventional ANDSF component located elsewhere can alsofacilitate ranking non-vendor ANRs associated with this conventionalinformation. As sated herein, ranking ANRs associated with conventionalANDSF information can be separate from, in parallel with, or inconjunction with ranking of a vendor ANR.

At 780, method 700 can comprise determining ANR selection informationbased on the ANR rank information from 760. Determining ANR selectioninformation can comprise analysis of information related to an ANR or aset of ANRs in view of the rank determination for an ANR.

At 790, method 700 can include facilitating access to the ANR selectioninformation. At this point method 700 can end. In some embodiments,access to the ANR selection information can be by a UE, such as thedevice associated with device information from 710.

FIG. 8 illustrates a method 800 that facilitates updating user profileinformation at a UE, via a vendor access network resource component, inresponse to receiving an access network resource rank by the vendoraccess network resource component in accordance with aspects of thesubject disclosure. At 810, method 800 can include receiving deviceinformation associated with a UE. The information can be received at avendor access network resource component. Device information cancomprise, in certain embodiments, current UE device states to enabledetermining ANR selection information. Current UE device states caninclude information about the current hardware and current softwareenvironments of the UE. This current information can reflect a resourceneed or resource preference sought from a prospective ANR, and selectionof an appropriate ANR can be facilitated by analyzing resourcesassociated with equipment of different vendors. In some embodiments,device information can comprise historic information, futureinformation, or event information, as disclosed herein.

At 820, method 800 can include facilitating access to VANR information.The access can be facilitated by the vendor access network resourcecomponent. VANR information can comprise vendor value added informationor vendor ANR parameter information related to an access networkresource, related to a vendor service or product related thereto,account information related to an a UE or user profile, etc. In someembodiments, VANR information can comprise event information, asdisclosed herein. In certain embodiments, VANR information can comprisecurrent or historical vendor ANR information, such as, ANR networkcongestion, available ANRs, billing agreements for ANRs with a networkprovider, vendor-centric selection rules, etc. The device informationcan also be accessed at 820.

At 830, method 800 can include receiving, at the VANR component, an ANRrank for an ANR, wherein the ANR rank is based on ANDSF information, thedevice information, and the VANR information. Determining an ANR rankcan comprise analysis of information related to an ANR or a set of ANRs.The information can reflect a suggested or prioritized ANR in accordwith TSANDSF functionality. ANR selection information can be based onVANR information, which can comprise current or historical vendor ANRinformation. ANR selection information can also be based on deviceinformation. In some instances, ranking or ordering an ANR can compriseranking or ordering a vendor ANR. Ranking or ordering an ANR can furtherbe based on receiving conventional ANDSF information, as disclosedelsewhere herein, such as ANDSF information received from a core networkcomponent associated with a cellular service provider core network.

At 840, method 800 can comprise the VANR component facilitating updatinguser profile information at a UE via a customer profile informationcomponent associated with the VANR component. This can be in response toreceiving, at the ANR rank by the VANR component. At this point, method800 can end. User profile information can comprise information relatedto user related preferences, user related facts, and use and userrelated opinions. User profile information can be considered in aTSANDSF analysis relating to selection of an ANR. A customer profileinformation component can facilitate access to information associatedwith a customer profile. Customer profile information can compriseinformation related to customer related preferences, customer relatedfacts, and use and customer related opinions. Customer profileinformation can be considered in a TSANDSF analysis relating toselection of an ANR. User profile information and customer profileinformation can, in some instances, comprise the same or similarinformation, for example where the information is shared eitherdirectly, via a TSANDSF component, or via another pathway. In certainembodiments, user profile information and customer profile informationcan be stored on the same data store or can be in extracted from thesame set of data. In an aspect, a customer profile informationcomponent, e.g., customer profile information component 338, canfacilitate access to user profile information. In some embodiments, userprofile information can be used to update customer profile information.In some embodiments, customer profile information can be used to updateuser profile information. As such, user profile information and customerprofile information can be updated to reflect information related touser preferences and customer preferences.

FIG. 9 is a schematic block diagram of a computing environment 900 withwhich the disclosed subject matter can interact. The system 900 includesone or more remote component(s) 910. The remote component(s) 910 can behardware and/or software (e.g., threads, processes, computing devices).In some embodiments, remote component(s) 910 can include servers,personal servers, wireless telecommunication network devices, etc. As anexample, remote component(s) 910 can be a mobile device, e.g., mobiledevice 220, 320, 420, etc., a VANR component, e.g., VANR component 230,330, 430, 432, 434, etc., a vendor-side component, e.g., 490, 492, 494,etc., an ANR, e.g., 450-452, 454, etc.

The system 900 also includes one or more local component(s) 920. Thelocal component(s) 920 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)920 can include a TSANDSF component, e.g., TSANDSF component 110, 210,310, 410, etc., a network provider side component 412, etc.

One possible communication between a remote component(s) 910 and a localcomponent(s) 920 can be in the form of a data packet adapted to betransmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 910 and a local component(s)920 can be in the form of circuit-switched data adapted to betransmitted between two or more computer processes in radio time slots.As an example, information related to a device hardware or softwareenvironment, vendor ANR parameters, vendor value added information, ANRselection information, ANDSF information, etc., can be communicated overa packet-switched or circuit-switched channels between remote component910, and a local component 920, via an air interface, such as on apacket-switched or circuit-switched downlink channel. The system 900includes a communication framework 940 that can be employed tofacilitate communications between the remote component(s) 910 and thelocal component(s) 920, and can include an air interface, e.g., Uuinterface of a UMTS network. Remote component(s) 910 can be operablyconnected to one or more remote data store(s) 950, such as an availableuser profile store, e.g., 328, customer profile store, e.g., 338, mobiledevice information store, VANR information store, etc., that can beemployed to store information on the remote component(s) 910 side ofcommunication framework 940. Similarly, local component(s) 920 can beoperably connected to one or more local data store(s) 930, that can beemployed to store information, such as received ANDSF information,received user profile information, e.g., 328, received customer profileinformation, e.g., 338, received mobile device information, receivedVANR information store, etc., on the local component(s) 920 side ofcommunication framework 940.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory,by way of illustration, and not limitation, volatile memory 1020 (seebelow), non-volatile memory 1022 (see below), disk storage 1024 (seebelow), and memory storage 1046 (see below). Further, nonvolatile memorycan be included in read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, or flash memory. Volatile memory can include random accessmemory, which acts as external cache memory. By way of illustration andnot limitation, random access memory is available in many forms such assynchronous random access memory, dynamic random access memory,synchronous dynamic random access memory, double data rate synchronousdynamic random access memory, enhanced synchronous dynamic random accessmemory, Synchlink dynamic random access memory, and direct Rambus randomaccess memory. Additionally, the disclosed memory components of systemsor methods herein are intended to comprise, without being limited tocomprising, these and any other suitable types of memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, including single-processor ormultiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,netbook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of TSANDSFcomponent 110, 210, 310, 410, etc., mobile device 220, 320, 420, VANRcomponent 230, 330, 430, 432, 434, 436, etc., or employing method 500,600, 700 or 800, etc., includes a processing unit 1014, a system memory1016, and a system bus 1018. System bus 1018 couples system componentsincluding, but not limited to, system memory 1016 to processing unit1014. Processing unit 1014 can be any of various available processors.Dual microprocessors and other multiprocessor architectures also can beemployed as processing unit 1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 1194), and small computer systems interface.

System memory 1016 can include volatile memory 1020 and nonvolatilememory 1022. A basic input/output system, containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1020 includes read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1012 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1024to system bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, flash memory or other memory technology, compact disk readonly memory, digital versatile disk or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or other tangible media which can be used tostore desired information. In this regard, the term “tangible” herein asmay be applied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating intangible signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can includenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. As an example, a user interface can allow entry ofuser profile information, 328, etc., e.g., user preferences, user facts,etc., customer profile information, 338, etc., e.g., customerpreferences, customer facts, etc., and can be embodied in a touchsensitive display panel, a mouse input GUI, a command line controlledinterface, etc., allowing a user to interact with computer 1012. Inputdevices 1036 include, but are not limited to, a pointing device such asa mouse, trackball, stylus, touch pad, keyboard, microphone, joystick,game pad, satellite dish, scanner, TV tuner card, digital camera,digital video camera, web camera, cell phone, smartphone, tabletcomputer, etc. These and other input devices connect to processing unit1014 through system bus 1018 by way of interface port(s) 1038. Interfaceport(s) 1038 include, for example, a serial port, a parallel port, agame port, a universal serial bus, an infrared port, a Bluetooth port,an IP port, or a logical port associated with a wireless service, etc.Output device(s) 1040 use some of the same type of ports as inputdevice(s) 1036.

Thus, for example, a universal serial busport can be used to provideinput to computer 1012 and to output information from computer 1012 toan output device 1040. Output adapter 1042 is provided to illustratethat there are some output devices 1040 like monitors, speakers, andprinters, among other output devices 1040, which use special adapters.Output adapters 1042 include, by way of illustration and not limitation,video and sound cards that provide means of connection between outputdevice 1040 and system bus 1018. It should be noted that other devicesand/or systems of devices provide both input and output capabilitiessuch as remote computer(s) 1044. As an example, vehicle subsystems, suchas headlights, brake lights, stereos, vehicle information sharingdevice, etc., can include an output adapter 1042 to enable use inaccordance with the presently disclosed subject matter.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies include fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies include, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “home Node B,” “home access point,” and thelike, are utilized interchangeably in the subject application, and referto a wireless network component or appliance that serves and receivesdata, control, voice, video, sound, gaming, or substantially anydata-stream or signaling-stream to and from a set of subscriber stationsor provider enabled devices. Data and signaling streams can includepacketized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include broadcasttechnologies (e.g., sub-Hertz, extremely low frequency, very lowfrequency, low frequency, medium frequency, high frequency, very highfrequency, ultra-high frequency, super-high frequency, terahertzbroadcasts, etc.); Ethernet; X.25; powerline-type networking, e.g.,Powerline audio video Ethernet, etc; femto-cell technology; Wi-Fi;worldwide interoperability for microwave access; enhanced general packetradio service; third generation partnership project, long termevolution; third generation partnership project universal mobiletelecommunications system; third generation partnership project 2, ultramobile broadband; high speed packet access; high speed downlink packetaccess; high speed uplink packet access; enhanced data rates for globalsystem for mobile communication evolution radio access network;universal mobile telecommunications system terrestrial radio accessnetwork; or long term evolution advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A system, comprising a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: in responseto receiving an identifier, receiving information related to a userprofile from a device associated with an access network discovery andselection function, wherein the information comprises an interestindicator, and wherein the information is associated with historical useinformation associated with the user profile; determining a commerceprovider value for a commerce provider wireless network device having aservice area comprising a location of a mobile device associated withthe user profile, wherein the commerce provider value is determinedbased on whether the commerce provider value satisfies a rule related tothe interest indicator; selecting the commerce provider wireless networkdevice based on the commerce provider value; and facilitating access toa commerce provider service feature via the mobile device connected tothe commerce provider wireless network device.
 2. The system of claim 1,wherein the interest indicator is associated with contemporary useinformation associated with the user profile.
 3. The system of claim 1,wherein the historical use information associated with the user profilecomprises historical preference information associated with a useridentity.
 4. The system of claim 1, wherein the interest indicator isassociated with inferred information associated with the user profilerelated to an inference with respect to a future use of the mobiledevice.
 5. The system of claim 1, wherein the interest indicator isassociated with use information associated with the user profile and adetermination of an event being determined to have occurred within apredetermined distance from the mobile device.
 6. The system of claim 1,wherein the facilitating the access to the commerce provider servicefeature comprises access to an advertisement related to a commerceprovider identity associated with the commerce provider wireless networkdevice.
 7. The system of claim 1, wherein the facilitating the access tothe commerce provider service feature comprises access to a definedpremium service tier provided by the commerce provider wireless networkdevice of a commerce provider identity.
 8. The system of claim 1,wherein the facilitating the access to the commerce provider servicefeature comprises facilitating access to an themed application interfacerelated to a commerce provider identity associated with the commerceprovider wireless network device.
 9. A method comprising: receiving, bya device comprising a processor, information comprising a stateindicator related to a mobile device state, wherein the device isassociated with an access network discovery and selection function, andwherein the state indicator is associated with historical useinformation associated with the mobile device; determining, by thedevice, a commerce provider value for a commerce provider wirelessnetwork device having a service area comprising a location of the mobiledevice, wherein the commerce provider value is determined based onwhether the commerce provider value satisfies a rule related to thestate indicator; selecting, by the device, the commerce providerwireless network device based on the commerce provider value; andfacilitating, by the device, access to a commerce provider servicefeature via the mobile device connected to the commerce providerwireless network device.
 10. The method of claim 9, wherein thereceiving the information comprises receiving the state indicatorassociated with contemporary use information associated with the mobiledevice.
 11. The method of claim 9, wherein the historical useinformation associated with the mobile device comprises historical factsassociated with a user identity.
 12. The method of claim 9, wherein thereceiving the information comprises receiving the state indicatorassociated with inferred information related to an inference withrespect to a future use of the mobile device.
 13. The method of claim 9,wherein the receiving the information comprises receiving the stateindicator associated with use information associated with the mobiledevice and a determination of an event being determined to have occurredwithin a predetermined distance from the mobile device.
 14. The methodof claim 9, wherein the facilitating the access to the commerce providerservice feature comprises access to information related to a commerceprovider value added feature associated with the commerce provider. 15.The method of claim 14, wherein the access to information related to acommerce provider value added feature comprises access to informationrelated to a discount offered by the commerce provider.
 16. The methodof claim 14, wherein the access to information related to a commerceprovider value added feature comprises access to information related toa service offered by the commerce provider via the mobile device afterconnecting to the commerce provider wireless network device.
 17. Amachine-readable storage device comprising executable instructions that,when executed by a processor, facilitate performance of operations,comprising: receiving information comprising an indicator related to amobile device software environment condition, wherein the informationcomprises receiving a state indicator associated with historical useinformation associated with the mobile device; determining a commerceprovider value for a commerce provider wireless network device having aservice area comprising a location of the mobile device, wherein thecommerce provider value is determined based on whether the commerceprovider value satisfies a rule related to the indicator; selecting thecommerce provider wireless network device based on the commerce providervalue; and facilitating access to a commerce provider service featurevia the mobile device connected to the commerce provider wirelessnetwork device.
 18. The computer-readable storage device of claim 17,wherein the historical use information associated with the mobile devicecomprises historical opinions related to a user identity.
 19. Thecomputer-readable storage device of claim 17, wherein the receiving theinformation comprises receiving the state indicator associated withinferred information related to an inference with respect to a futureuse of the mobile device.
 20. The computer-readable storage device ofclaim 17, wherein the facilitating the access to the commerce providerservice feature comprises access to information related to a commerceprovider value added feature associated with the commerce provider.